|
|
||||
| InfoRMS | ||||
| Displaying 11 issues at 16/Jul/25 10:49 AM. |
| Key | Summary | Description | Resolution | Resolution Description |
|---|---|---|---|---|
| PS-213 | Make Patient.Address.line MS |
Summary: Make Patient.Address.line MS
Existing Wording: Proposed Wording: Comment: Add MS to Patient.Address.line Submitted by: CA Core + Team Infoway |
Persuasive | Add MS to the elements to match CA-Core |
| PS-212 | IPS CI build changed to 0..* non MS; previously 1..1 MS; PS-CA should change back |
DiagnosticReport.Category MS and cardinality differences
CA Core+ = 0..* non MS PS-CA = 1..1 MS IPS CI build changed to 0..* non MS; previously 1..1 MS; PS-CA should change back |
Persuasive | Change DiagnosticReport.category to 0..* with no MS |
| PS-211 | PSCA should change binding strenght to extensible to align with Core since both ValueSets are the same |
Summary: PSCA should change binding strenght to extensible to align with Core since both ValueSets are the same
Existing Wording: Proposed Wording: Comment: ImagingStudy.procedureCode binding CA Core+ http://radlex.org (extensible) PS-CA RadLex_Playbook.aspx (example) PSCA should change binding strenght to extensible to align with Core since both ValueSets are the same Submitted by: CA Core + Team Infoway |
Persuasive | Update binding to extensible to align with R4 and CA Core.
|
| PS-209 | Make Patient.address.postalCode MS |
Summary: Make Patient.address.postalCode MS
Existing Wording: Proposed Wording: Comment: Add MS to Patient.address.postalCode Submitted by: CA Core + Team Infoway |
Persuasive | Add the MS flag |
| PS-208 | Make Patient.Address.country MS |
Summary: Make Patient.Address.country MS
Existing Wording: Proposed Wording: Comment: Add MS to Patient.Address.country Submitted by: CA Core + Team Infoway |
Persuasive | Add MS flag |
| PS-207 | Make Patient.Address.City MS |
Summary: Make Patient.Address.city MS
Existing Wording: Proposed Wording: Comment: Add MS to Patient.Address.city Submitted by: CA Core + Team Infoway |
Persuasive | Add the MS flag |
| PS-206 | PS-CA should change to 1..*, to match Core since the slice in PS-CA is patterned |
Summary: PS-CA should change to 1..*, to match Core since the slice in PS-CA is patterned
Existing Wording: Proposed Wording: Comment: Observation-SocialHistory.Category CA Core+ 1…* PS-CA 0…* PS-CA should change to 1..*, to match Core since the slice in PS-CA is patterned Submitted by: CA Core + Team Infoway |
Persuasive | Tighten ObservationSocialHistory category element from 0..* to 1..* to align with CA Core+ |
| PS-205 | Can PS-CA consider adding PHCVS and HealthConditionCode binding to PS-CA without adding a Must Support flag ? |
Summary: Can PS-CA consider adding PHCVS and HealthConditionCode binding to PS-CA without adding a Must Support flag ?
Existing Wording: Proposed Wording: Comment: Medication Statement.reasonCode binding CA Core+ : PHCVS (Preferred) , HealthConditionCode(Candidate) PS-CA : Condition/Problem/DiagnosisCodes (example) (baseFHIR) Can PS-CA consider adding PHCVS and HealthConditionCode binding to PS-CA without adding a Must Support flag ? Submitted by: CA Core + Team Infoway |
Persuasive | Add a preferred binding to PHCVS with an additional binding of HealthConcernCode (candidate) |
| PS-204 | Make authoredOn MS |
Summary: Make authoredOn MS
Existing Wording: Proposed Wording: Comment: MedicationRequest.authoredOn CA Core 0..1 MS PS-CA 0..1 non MS (Base FHIR) Make authoredOn MS Submitted by: CA Core+ Team Infoway |
Persuasive | Add MS flag to authoredOn to align with CA Core |
| PS-86 | Suggestion on adding granularity in defining MustSupport elements for: (Patient/Practitioner).telecom |
Summary: Suggestion on adding granularity in defining MustSupport elements for: (Patient/Practitioner).telecom
Existing Wording: Proposed Wording: Comment: The level of granularity for MustSupport (MS) elements remains an ongoing issue. During the Patient Summary LPR in Ontario the EMR vendors requested for OH to provide additional guidance on what specific child elements to be included in their PS data contribution. It would be beneficial for the PS-CA WG to collaborate and explore opportunities to define more specific guidance to improve consistency and reduce variations between the implementations across jurisdictions Submitted by: Cindy Jiang ([email protected]) Philip Sales ([email protected]) OntarioHealth |
Persuasive with Modification | Align with CA Core, adding MS to Patient.telecom but not Practitioner.telecom |
| PS-85 | Suggestion on adding granularity in defining MustSupport elements for: Patient.address |
Summary: Suggestion on adding granularity in defining MustSupport elements for: Patient.address
Existing Wording: Proposed Wording: Comment: The level of granularity for MustSupport (MS) elements remains an ongoing issue. During the Patient Summary LPR in Ontario the EMR vendors requested for OH to provide additional guidance on what specific child elements to be included in their PS data contribution. It would be beneficial for the PS-CA WG to collaborate and explore opportunities to define more specific guidance to improve consistency and reduce variations between the implementations across jurisdictions Submitted by: Cindy Jiang ([email protected]) Philip Sales ([email protected]) OntarioHealth |
Persuasive | Add MS to elements to align with CA-Core |
| Generated at Wed Jul 16 10:49:57 EDT 2025 by Sonia Balgah using Jira 10.3.2#10030002-sha1:0a5d322ae1b7fd5b314be5b31a27d9661f8301b2. |